-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recreate AEH Processor in the event of an error before retrying the processing operation #3614
Conversation
Recreate AEH Processor in the event of an error before retrying the processing operation Signed-off-by: MattCosturos <[email protected]>
See failing build tests |
Updated to log the initial connection error, and then retry after 5 seconds. Same way we handle errors after the initial creation. |
…processing events in Azure Event Hubs subscription. Signed-off-by: Matt Costuros <[email protected]>
Signed-off-by: Matt Costuros <[email protected]>
Signed-off-by: Matt Costuros <[email protected]>
/ok-to-test |
Complete Build MatrixThe build status is currently not updated here. Please visit the action run below directly. Commit ref: 3a2da6f |
Components conformance testCommit ref: 3a2da6f ❌ Some conformance tests failedThese tests failed:
|
Components certification testCommit ref: 3a2da6f ❌ Some certification tests failedThese tests failed:
|
@artursouza for last review |
@holopin-bot @MattCosturos Thank you! |
Congratulations @MattCosturos, the maintainer of this repository has issued you a badge! Here it is: https://holopin.io/claim/cm5qy4cgt31630cmjrmpc4am6 This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Recreate AEH Processor in the event of an error before retrying the processing operation
Description
Moved the creation and setup of the Azure Event Hub Processor inside the main loop.
The processor.run only returns a non-recoverable error. Therefore we must re-create new processor and setup the subscription.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #3573
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: